home *** CD-ROM | disk | FTP | other *** search
-
-
-
- EEEExxxxttttUUUUttttiiiillllssss::::::::MMMMkkkkbbbboooooooottttssssttttrrrraaaapppp((((3333)))) EEEExxxxttttUUUUttttiiiillllssss::::::::MMMMkkkkbbbboooooooottttssssttttrrrraaaapppp((((3333))))
-
-
-
- NNNNAAAAMMMMEEEE
- ExtUtils::Mkbootstrap - make a bootstrap file for use by DynaLoader
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- mkbootstrap
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- Mkbootstrap typically gets called from an extension Makefile.
-
- There is no *.bs file supplied with the extension. Instead a *_BS file
- which has code for the special cases, like posix for berkeley db on the
- NeXT.
-
- This file will get parsed, and produce a maybe empty
- @DynaLoader::dl_resolve_using array for the current architecture. That
- will be extended by $BSLOADLIBS, which was computed by
- _E_x_t_U_t_i_l_s::_L_i_b_l_i_s_t::_e_x_t(). If this array still is empty, we do nothing,
- else we write a .bs file with an @DynaLoader::dl_resolve_using array.
-
- The *_BS file can put some code into the generated *.bs file by placing
- it in $bscode. This is a handy 'escape' mechanism that may prove useful
- in complex situations.
-
- If @DynaLoader::dl_resolve_using contains -L* or -l* entries then
- Mkbootstrap will automatically add a _d_l__f_i_n_d_f_i_l_e() call to the generated
- *.bs file.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-